test(missions): synchronize compact-form fixture reads and publication - #1407

The current workspace lockfile references windows-sys 0.60.2 in muda, socket2, tray-icon, uds_windows and window-vibrancy, but contains no package record for that version. Cargo validates the whole lock graph before filtering by target, so both Linux and macOS reject it with --locked. The inconsistent edges entered dev with the WebKit preview merge and are independent of the npm dependency catch-up.

Point only these five edges at the already-locked windows-sys 0.61.2, which every parent's declared range accepts. No package versions, sources, checksums, other dependency edges or vendored patch selections change. Retain all --locked gates.

The original reproduces the refusal with a fresh private Cargo cache. Corrected cargo metadata --locked --offline succeeds with macOS ARM64, Linux x64 and Windows x64 target filters; six existing vendor tests pass. Independent byte comparison confirms exactly five substitutions, and the three locked metadata checks were independently reproduced. Native compilation remains for CI.

The corrected Cargo graph passes all five native Tauri jobs, but the baseline still fails its build-order contract and contextual-help browser test. Require the already-present WebKit job in the exact build dependency assertion; this is the same hunk carried by #1305. Await the third native help-opening receipt before the existing URL assertion; this is the one-line correction from #1410.

Keep every production change confined to the five already-reviewed lock edges. No assertion is removed, no deadline changes, and the helper opening must complete before its destination is checked. Merge current dev, which also contains the WebKit fixture-wiring correction. The independent recurrence-Pause flake is still under investigation; a green rerun is not its explanation.

…tinuing

Failure-time CI evidence shows Daily's Pause disabled at pointer-down and pointer-up with no click, after the other row's partial Pause. The helper awaited local unconfirmed feedback, but that result also starts a row refresh; its loading guard can disable actions between Playwright's actionability check and pointer delivery.

Wait for the owning row to publish Paused or Stopped before advancing the next test action. Keep every existing assertion, deadline and retry unchanged; no forced click or product change. A held read proves the original helper returned too early, while the corrected helper waits for publication. The 22 targeted browser tests pass, independently rerun on Node 24.22.2.

…owner

The strict failed-request collector retained cancellations from project discovery, not just Create. A later remembered model option could not prove that either the initial or replacement catalog reader had completed. Separately, the test fixture awaited its display fetch before retiring the saved editor, allowing another catalog read that production MissionControl never starts.

Passively retain exact request-finished receipts during navigation, consume the initial wave after fixture load, and immediately own the discovery wave with Promise.all around its trigger. Close the fixture editor synchronously before its display fetch, matching the real UI owner. Keep the existing assertions, cancellation collector and default navigation/action bounds unchanged; no forced clicks, sleeps or failed-request filters.

All six controlled original-head failure scenarios pass with the correction, including either agent/model completion order and late display reads. Seven targeted tests pass with exact Node 24.22.2/npm 11.19.1/Solid 1.9.18 dependencies, independently repeated. Virtual-clock controls confirm navigation is not shortened by prematurely armed action timeouts.

#1305 already supplies the Cargo graph repair, build-order contract, native-help receipt synchronization and manifest-test compatibility. Keep its implementation and controlled tests rather than overwriting them with alternative fixes from this branch. The resulting diff against dev contains only five Missions test/fixture files.

Retain the proven catalog-wave receipts, synchronous editor retirement, partial-result publication wait and compact-form fixture corrections. All 46 targeted tests pass on a fresh current-dev source snapshot with the exact lock-matched dependencies and Node 24.22.2. No assertion, deadline, retry or failed-request filtering changes. Full CI must run on this new combination; no force push.